Update RuboCop settings and apply automatic corrections #332
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aeroastro
force-pushed
the
feature/rubocop-update
branch
from
26767e9
to
cf91112
Compare
This was referenced Mar 11, 2021
This was referenced Mar 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RuboCop was introduced by #226 2 years ago, but there are some missing settings.
In this PR, I would like to change the followings so that we can check code easily and correctly.
zipruby.gemspecfor developer friendlinessbundle exec rubocop -aIf we are not satisfied with default rubocop style, we can modify the rules at
.rubocop.ymlafterward.